fix: configure CORS via env ALLOWED_ORIGINS#581
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
No CORS was configured in
main.ts, allowing any origin to connect. This fix adds an env-driven CORS allowlist (ALLOWED_ORIGINS) so only explicitly listed origins are permitted in production.Changes
app/backend/src/main.ts: enable CORS with origin allowlist fromprocess.env.ALLOWED_ORIGINS(comma-separated). Credentials are only passed when the origin is in the allowlist. Methods limited toGET/POST/PUT/PATCH/DELETE/OPTIONS.app/backend/.env.example: documentALLOWED_ORIGINSwith a sensible local default.Testing
ALLOWED_ORIGINS=http://localhost:3000→Origin: http://localhost:3000preflight returnsAccess-Control-Allow-Origin.Access-Control-Allow-Originheader returned.Closes #519